xsm: Expand I/O resource hooks
authorDaniel De Graaf <dgdegra@tycho.nsa.gov>
Fri, 2 Dec 2011 21:47:08 +0000 (13:47 -0800)
committerDaniel De Graaf <dgdegra@tycho.nsa.gov>
Fri, 2 Dec 2011 21:47:08 +0000 (13:47 -0800)
commit3d7895b3bbe977e3abd2d4128e42c1daba5e3fa4
tree3a17a23357b787f377dc3dc669824cc88e352306
parent65d744c6d56f92401b9d279c9cf8fe618397be0e
xsm: Expand I/O resource hooks

The XSM hooks inside rangeset are not useful in capturing the PIRQ
mappings in HVM domains. They can also be called from softirq context
where current->domain is invalid, causing spurious AVC denials from
unrelated domains on such calls.

Within FLASK code, the rangeset hooks were already divided between
IRQs, I/O memory, and x86 IO ports; propagate this division back
through the XSM hooks and call the XSM functions directly when needed.

This removes XSM checks for the initial rangeset population for dom0
and the removal checks on domain destruction; denying either of these
actions does not make sense.

Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Committed-by: Keir Fraser <keir@xen.org>
xen/arch/x86/domctl.c
xen/arch/x86/irq.c
xen/arch/x86/physdev.c
xen/common/domctl.c
xen/common/rangeset.c
xen/include/xsm/xsm.h
xen/xsm/dummy.c
xen/xsm/flask/hooks.c